Found those three properties completely randomly on a completely unrelated topic post...

Dropping them right here, just in case someone needs it :

clip: true boundsBehavior: Flickable.DragAndOvershootBounds snapMode: ListView.SnapToItem

They're doing about everything i need. I think that's a common problem beginners fall into but there is not that much topics about it.

Hi! Thanks for reporting this. You can find the bug database at https://bugreports.qt.io

need to check Qt classes for system settings and native look and feel,
and of adopting those changes for App.

Thanks,

ok. Let us look at like this. Instead of web view, put the Rectangle{}
Try to show & hide the rectangle instead of web-view. Till me whether it works or not.
Try something like this
OffLine_Pages.qml

Pane{ id: view property string local_url : "" property string pid : "" property alias vis: web.visible Rectangle{ id : web width: 200;height: 200;color: "red" visible: false } }

That's it @Eeli-K
Thanks a lot

@JKSH That's it

Thank you guys.

@chaithubk
whenever data relevant for drawing has changed call update() on the QQuickItem and a call to updatePaintNode() (-> painting) is scheduled.
Like in is mentioned in the link to the docs i've posted.

I found some kind of workaround that helps me with it, but I'm not sure if it is very smooth solution. Here is a new code for window creation:

QQmlEngine *engine = new QQmlEngine; MyWindow *window = new MyWindow (engine); window->setSource(...); window->rootContext()->setContextProperty("window", window); window->show();

With this each window is associated with the correspondng QObject. But is it a good solution - to create separate QQmlEngine for each window?

Also, was hab ich jetzt abschließend gemacht?
Da meine Qt Kenntnisse (noch) nicht ausreichen, um vernünftig mit styleplugins zu arbeiten, habe ich zu Linux Mint 18.1 KDE gewechselt. Wollte ich eh schon länger. Dort wird das passende Theme verwendet. :-)

Es gibt auch mehrere Bug-Reports für den Cinnamon Desktop unter Linux Mint, die alle das gleiche Problem mit Qt >=5.7 haben. Eine passende Lösung für mich konnte ich nicht finden.

Grüße,
Andre

I had create a model with key and value and pass it to qml, it worked!!!
Sorry for late reply.
Thank you @raven-worx

To build QtCharts calling

qmake CONFIG+=debug_and_release make debug make release make install

should be enough to build and install it

@p3c0

Thanks a lot.

@lorow23

but how I should acces particular rectangles then?

With the model approach it wont be required. The delegate items will get the data from model. Also when required you just need to update the model with new data from the delegate or from outside.
For eg. ListModel has several methods to access the data.

@Mathan-M said:

appWindow.timeChanged()

Where is that time property? Also, if there would be such a property, then timeChanged would be a signal.

First a note that SwipeView and its base type Container have gained some new members in Qt Quick Controls 2.1 in the upcoming Qt 5.8. These will help with your tasks:

SwipeView::interactive Container::incrementCurrentIndex() Container::decrementCurrentIndex()

For the time being, you could add the following binding as a temporary workaround until you will be able to use the new public interactive property:

Binding { property: "interactive" target: swipeView.contentItem value: swipeView.currentIndex !== indexOfWebEngineView }

@Newsages I've been building for Boundary Devices Sabrelite board (MACHINE=nitrogen6x). I have not tried to build for the emulator.

I can't say that I understood your code, but if you'll change the return value of your reading method (read(), I presume) to QStringList, then you can display it with ListView in QML like this:

ListView { //Layout.preferredHeight: childrenRect.height model: myFile.read() delegate: Text { text: modelData } }

You're welcome !

Since you have now material to go on, please mark the thread as solved using the "Topic Tools" button so that other forum users may know an answer has been found :)